Methods and apparatus for building a three-dimensional model from multiple data sets

ABSTRACT

Methods and apparatus for a map tool displaying a three-dimensional view of a map based on a three-dimensional model of the surrounding environment. The three-dimensional map view of a map may be based on a model constructed from multiple data sets, where the multiple data sets include mapping information for an overlapping area of the map displayed in the map view. For example, one data set may include two-dimensional data including object footprints, where the object footprints may be extruded into a three-dimensional object based on data from a data set composed of three-dimensional data. In this example, the three-dimensional data may include height information that corresponds to the two-dimensional object, where the height may be obtained by correlating the location of the two-dimensional object within the three-dimensional data.

This application claims benefit of priority to U.S. ProvisionalApplication Ser. No. 61/655,811, entitled “Methods and Apparatus forBuilding a Three-Dimensional Model from Multiple Data Sets,” filed Jun.5, 2012.

BACKGROUND

Mobile and desktop devices often provide various map related functions,including map views and navigation capabilities. Within a map view of amap application executing on a mobile or desktop device, a user mayprefer to see a representation of the surrounding environment in anaesthetically simple rendering. For example, as a user walks down astreet referencing the map view provided by a mobile device, a user mayfind it easier to navigate if surrounding structures in the map viewwere stripped of unnecessary and distracting details, texture or otherinformation that may not be related to navigation or identification ofthe structure. In some cases, the map view may be three-dimensional, andin such a case a map view that is a simplified version of the real worldmay allow a user to make quicker navigation decisions.

SUMMARY

In one embodiment, a mobile device or desktop computer may receivemapping information, which the mobile device or desktop computer may useto construct a three-dimensional map view of a map on a display. Thethree-dimensional map view of a map may be based on a model constructedfrom multiple data sets, where the multiple data sets include mappinginformation for an overlapping area of the map displayed in the mapview.

In some cases, the three-dimensional model may be constructed fromtwo-dimensional and three-dimensional data. For example, one data setmay include two-dimensional data including object footprints, where theobject footprints may be extruded into a three-dimensional object basedon data from a data set composed of three-dimensional data. In thisexample, the three-dimensional data may include height information thatcorresponds to the two-dimensional object, where the height may beobtained by correlating the location of the two-dimensional objectwithin the three-dimensional data.

The granularity of the constructed model may be varied, however, theconstructed model may often be less cluttered than if highly detailedthree-dimensional data or raster data were used to render a map view.The constructed model may therefore provide a cleaner rendering of thesurrounding environment and a more efficient map using experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is an illustration of a portable multifunction device suitableto implement a map tool, according to some embodiments.

FIG. 1B is a diagram illustrating example components within a portablemultifunction device suitable for implementing a map tool, according tosome embodiments.

FIG. 2 illustrates a touch screen on a multifunction device, accordingto some embodiments.

FIG. 3 illustrates another multifunction device configurable toimplement a mapping application and map tool, according to someembodiments.

FIGS. 4A-4E depict example flowcharts corresponding to differentembodiments of a map tool, according to some embodiments.

FIGS. 5A-5D depict illustrations of different viewpoints available in amap view, according to some embodiments.

FIG. 6 illustrates map tool module, according to some embodiments.

FIG. 7 depicts an illustration of a client/server architecture that maybe used in some embodiments of the map tool.

FIG. 8 depicts an illustration of a cloud computing environment that maybe used in some embodiments of the map tool.

FIG. 9 depicts elements of a map service operating environment,according to some embodiments.

FIG. 10 depicts elements of an example computer system capable ofimplementing a map tool.

While the invention is described herein by way of example for severalembodiments and illustrative drawings, those skilled in the art willrecognize that the invention is not limited to the embodiments ordrawings described. It should be understood that the drawings anddetailed description are not intended to limit the invention to theparticular forms disclosed, but on the contrary, the intention is tocover all modifications, equivalents and alternatives falling within thespirit and scope of the present invention. The headings used are fororganizational purposes only and are not meant to be used to limit thescope of the description. As used throughout this application, the word“may” is used in a permissive sense (meaning “having the potential to”),rather than the mandatory sense (meaning “must”). Similarly, the words“include”, “including”, and “includes” mean “including, but not limitedto.”

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments are presented of a map tool displaying athree-dimensional view of a map, where the map tool bases thethree-dimensional view on a model constructed from one or more data setswith mapping information corresponding to the map.

In some cases, the map tool may generate a three-dimensional model usingelements from a two-dimensional data set of mapping information and froma three-dimensional data set of mapping information. For example,two-dimensional maps specifying locations and boundaries of variousstructures may be available to define the footprint of a given object orstructure in a map area. In this example, three-dimensional mesh datacorresponding to the map area may also be available, where within thehighly-detailed set of data is information regarding heights of objectsfor a given location within the map area. The map tool may use thefootprint for an object derived from the two-dimensional mappinginformation and extrude, or extend, the footprint into three-dimensionalspace using one or more height values, where the one or more heightvalues correspond to one or more points within the footprint. In somecases, the height values are determined from three-dimensional mappinginformation. This process may be repeated for each object footprint inthe map area, and once each object has been similarly processed, theresult is a model of a three-dimensional space for the map area derivedfrom multiple data sets from which a map view may be rendered.

An aspect of the three-dimensional model constructed from the two datasets is that the model may not accurately represent the shape of a givenbuilding. For example, if for a given footprint a single point in thecenter of the footprint were correlated to the corresponding point inthe three-dimensional mapping information, the footprint for the objectmay be extruded to the height of the point. However, it may be the casethat the top of the object may not be flat. In other words, if a givenobject has anything but a flat top, there may be multiple height valuescorresponding to different points within the object footprint. Tocompensate for the potential inaccuracy, the map tool may, in somecases, use multiple points to determine a height, or in some cases,determine multiple height values. While the constructed model may lacksome accuracy, what is gained is a decrease in computational complexity.

In some embodiments, the map tool may generate a three-dimensional modelusing footprint data from a two-dimensional data set and a height valuecorresponding to the footprint. For example, the map tool may receivemapping information that includes coordinates for various footprints ofvarious structures within a map region, and the mapping information mayalso include a single height value corresponding to each footprint. Inthis way, the map tool may, for each footprint in a map region, extrudea respective footprint within the map region according to a respectiveheight value for the respective footprint. Once each footprint has beenextruded, the map tool may render a three-dimensional map viewrepresenting the map region, where the three-dimensional map view isbased on the extruded footprints within the map region.

Mobile devices may provide a user with map navigation that includes athree-dimensional view corresponding to a current position. In somecases, the three-dimensional view may be constructed based on GlobalPositioning System (GPS) data, map information from other sources, orbased on GPS data combined with map information from other sources. Insome cases, a map view may be constructed from map informationcorresponding to a given address or to some other piece of informationfrom which location information may be derived. For example, from anypoint on earth, a user may give a voice command to the map tool, such as“show me the front of the Metropolitan Museum of Art in New York City.”In response to the voice command, the map tool, may access mapinformation for the location of the Metropolitan Museum of Art in NewYork City and generate a map view to the user.

However, a map view presented to a user through a traditional mappingapplication on a mobile device may present a user with photographicdetail of the surrounding environment. In some cases, the map view mayinclude cars, buses, bicycles, bicycle riders, pedestrians, and otherrandom objects, signs, or advertisements. A result may be a clutteredmap view that may decrease the efficiency with which a user may navigatethrough the map area. Therefore, it may be beneficial, or moreproductive, for a user to have the option to see a simplified version ofthe surrounding environment. For example, a user may select aconfiguration setting to display, within a map view of a mapapplication, an isometric view of structures drawn without texturing, orwithout any objects that are not structures. In some cases, a simplifiedmap view may be a default setting, requiring no action from a user toenable.

In some embodiments, the map view provides a user with a bird's eyevirtual camera view with photographic detail of the surroundingenvironment. In other embodiments, the map view provides a user withground level virtual camera view from the perspective of the user'slocation within the displayed map area. In other embodiments, a user maychoose the virtual camera perspective location from which the map viewmay be generated.

In some cases, the map view may be composed of various geometric figuresand may be considered a low resolution proxy of the actual, or highresolution version of the surrounding environment. In either the bird'seye view, ground level view, or the isometric view of geometric figures,the map tool may use one or more sources of map information to constructthe map view. In some cases, a data source containing of two-dimensionalinformation may be combined with another data source containingthree-dimensional information in order to generate a three-dimensionalmap view. In other cases, a three-dimensional source of mappinginformation alone may serve as a basis on which to construct athree-dimensional model of the surrounding environment.

In some cases, a user may manipulate a given map view such as throughinput indicating to the map tool to display a different virtual cameraperspective of the map view. For example, within a given map view, auser may wish to see the map view from the other side of a building.However, given that the previously generated model of the map view hasalready been constructed, the map tool does not need to generate a new3D model of the map view because the locations and spatial dimensions ofobject in the previously generated model remain valid for the newvirtual camera perspective.

In an embodiment, three-dimensional (3D) data may be 3D mesh data, whichmay contain data defining the location and orientation of thousands oftriangles for a given map view. Further in this embodiment,two-dimensional (2D) data may be obtained from maps for a given city orcounty which define the locations and the dimensions of footprints forstructures, roads, sidewalks, plazas, or other objects. In thisembodiment, in the interest of speed and computational complexity, a 3Dproxy may be constructed through the transformation of the 2D model intoa 3D model using selected pieces of information from the 3D model toenhance the 2D model. For example, if the 2D model provides informationregarding the footprint of a given building, the map tool may thenreference the 3D model to identify the corresponding location of thefootprint of the building. Once the location of the footprint of thebuilding is determined in the 3D model, one or more height values may beextracted from the 3D model for the building. Now, given the footprintof the building and the one or more height values, a rough box orpolygon may be extruded to one of the height values, or to some valuederived from the height values in order to generate an approximate 3Dshape. This process may be repeated for each object in the 2D data,thereby creating a rough, low-resolution version of the surroundingenvironment.

In some embodiments, a single source of data may be used, for example,the 3D mesh data for the surrounding environment. In this example, atwo-dimensional grid may be created, where each grid segment may beextruded based on a height value from the 3D mesh data, where the heightvalue from the 3D mesh data is for a location corresponding to the gridsegment. In the case where a given object in the map space overlaps withmultiple grid segments, the display of adjacent grid segments may besmoothed into a contiguous three-dimensional object. In this way, a 3Dmodel of the map space may be constructed using only height valuesextracted from the 3D mesh data.

In different embodiments, the map tool may adjust the granularity of theconstructed 3D model based on various factors. For example, a user maychoose a configuration setting to display different levels of detail inthe 3D model, and in response, the map tool may construct the 3D modelusing additional information from the one or more source data sets ofmapping information.

Detailed Description Considerations

In the following detailed description, numerous details are set forth toprovide a thorough understanding of the claimed subject matter. However,it will be understood by those skilled in the art that the claimedsubject matter may be practiced without these specific details. In otherinstances, methods, apparatus or systems that would be known by one ofordinary skill have not been described in detail so as not to obscureclaimed subject matter.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the device is a gaming computer withorientation sensors (e.g., orientation sensors in a gaming controller).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

Some portions of the detailed description which follow are presented interms of algorithms or symbolic representations of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and is generally, considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent from the following discussion, it is appreciatedthat throughout this specification discussions utilizing terms such as“processing”, “computing”, “calculating”, “determining”, or the likerefer to actions or processes of a specific apparatus, such as a specialpurpose computer or a similar special purpose electronic computingdevice. In the context of this specification, therefore, a specialpurpose computer or a similar special purpose electronic computingdevice is capable of manipulating or transforming signals, typicallyrepresented as physical electronic or magnetic quantities withinmemories, registers, or other information storage devices, transmissiondevices, or display devices of the special purpose computer or similarspecial purpose electronic computing device.

Example Multifunction Device

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 100 may includememory 102 (which may include one or more computer readable storagemediums), memory controller 122, one or more processing units (CPU's)120, peripherals interface 118, RF circuitry 108, audio circuitry 110,speaker 111, microphone 113, input/output (I/O) subsystem 106, otherinput or control devices 116, and external port 124. Device 100 mayinclude one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 1A may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU 120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may be implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of multiple communications standards, protocols and technologies,including but not limited to Global System for Mobile Communications(GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packetaccess (HSDPA), high-speed uplink packet access (HSUPA), wideband codedivision multiple access (W-CDMA), code division multiple access (CDMA),time division multiple access (TDMA), Bluetooth, Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input controldevices 116 may include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 may becoupled to any (or none) of the following: a keyboard, infrared port,USB port, and a pointer device such as a mouse. The one or more buttons(e.g., 208, FIG. 2) may include an up/down button for volume control ofspeaker 111 and/or microphone 113. The one or more buttons may include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any ofmultiple touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image may be obtained for videoconferencingwhile the user views the other video conference participants on thetouch screen display.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. In some embodiments, the proximity sensor turnsoff and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 includes one or more orientation sensors 168. In someembodiments, the one or more orientation sensors include one or moreaccelerometers (e.g., one or more linear accelerometers and/or one ormore rotational accelerometers). In some embodiments, the one or moreorientation sensors include one or more gyroscopes. In some embodiments,the one or more orientation sensors include one or more magnetometers.In some embodiments, the one or more orientation sensors include one ormore of global positioning system (GPS), Global Navigation SatelliteSystem (GLONASS), and/or other global navigation system receivers. TheGPS, GLONASS, and/or other global navigation system receivers may beused for obtaining information concerning the location and orientation(e.g., portrait or landscape) of device 100. In some embodiments, theone or more orientation sensors include any combination oforientation/rotation sensors. FIG. 1A shows the one or more orientationsensors 168 coupled to peripherals interface 118. Alternately, the oneor more orientation sensors 168 may be coupled to an input controller160 in I/O subsystem 106. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more orientationsensors.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which may be made up of a        video player    -   module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conference 139,e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of multiple communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 1493, alarmclock widget 149-4, and dictionary widget 149-5) or created by the user(e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 may include the functionality ofan MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 102 maystore a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,orientation sensor(s) 168, and/or microphone 113 (through audiocircuitry 110). Information that peripherals interface 118 receives fromI/O subsystem 106 includes information from touch-sensitive display 112or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes multiple event handlers190 and one or more application views 191, each of which includesinstructions for handling touch events that occur within a respectiveview of the application's user interface. Each application view 191 ofthe application 136-1 includes one or more event recognizers 180.Typically, a respective application view 191 includes multiple eventrecognizers 180. In other embodiments, one or more of event recognizers180 are part of a separate module, such as a user interface kit (notshown) or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 may utilize or call data updater 176, objectupdater 177 or GUI updater 178 to update the application internal state192. Alternatively, one or more of the application views 191 includesone or more respective event handlers 190. Also, in some embodiments,one or more of data updater 176, object updater 177, and GUI updater 178are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, includes a first touch (touch begin) on thedisplayed object for a predetermined phase, a first lift-off (touch end)for a predetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(187-2) is a dragging on a displayed object. The dragging, for example,includes a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making a gesture on the graphics, for example,with one or more fingers 202 (not drawn to scale in the figure) or oneor more styluses 203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thegesture may include one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 100 also may accept verbal inputfor activation or deactivation of some functions through microphone 113.

It should be noted that, although many of the following examples will begiven with reference to inputs on touch screen 112 (where the touchsensitive surface and the display are combined), a touch-sensitivesurface that is separate from the display may be used instead of touchscreen 112.

Map Service Operating Environment

Various embodiments of a map tool may operate within a map serviceoperating environment. FIG. 9 illustrates a map service operatingenvironment, according to some embodiments. A map service 930 mayprovide map services for one or more client devices 902 a-902 c incommunication with the map service 930 through various communicationmethods and protocols. A map service 930 generally may provide mapinformation and other map-related data, such as two-dimensional mapimage data (e.g., aerial view of roads utilizing satellite imagery),three-dimensional map image data (e.g., traversable map withthree-dimensional features, such as buildings), route and directioncalculation (e.g., ferry route calculations or directions between twopoints for a pedestrian), real-time navigation data (e.g., turn-by-turnvisual navigation data in two or three dimensions), location data (e.g.,where is the client device currently located), and other geographic data(e.g., wireless network coverage, weather, traffic information, ornearby points-of-interest). In various embodiments, the map service datamay include localized labels for different countries or regions;localized labels may be utilized to present map labels (e.g., streetnames, city names, points of interest) in different languages on clientdevices. Client devices 902 a-902 c may utilize these map services byobtaining map service data. Client devices 902 a-902 c may implementvarious techniques to process map service data. Client devices 902 a-902c may then provide map services to various entities, including, but notlimited to, users, internal software or hardware modules, and/or othersystems or devices external to the client devices 902 a-902 c.

In some embodiments, a map service may be implemented by one or morenodes in a distributed computing system. Each node may be assigned oneor more services or components of a map service. Some nodes may beassigned the same map service or component of a map service. A loadbalancing node may distribute access or requests to other nodes within amap service. In some embodiments a map service may be implemented as asingle system, such as a single server. Different modules or hardwaredevices within a server may implement one or more of the variousservices provided by a map service.

A map service may provide map services by generating map service data invarious formats. In some embodiments, one format of map service data maybe map image data. Map image data may provide image data to a clientdevice so that the client device may process the image data (e.g.,rendering and/or displaying the image data as a two-dimensional orthree-dimensional map). Map image data, whether in two or threedimensions, may specify one or more map tiles. A map tile may be aportion of a larger map image. Assembling together the map tiles of amap may produce the original map. Tiles may be generated from map imagedata, routing or navigation data, or any other map service data. In someembodiments map tiles may be raster-based map tiles, with tile sizesranging from any size both larger and smaller than a commonly-used 256pixel by 256 pixel tile. Raster-based map tiles may be encoded in anynumber of standard digital image representations including, but notlimited to, Bitmap (.bmp), Graphics Interchange Format (.gif), JointPhotographic Experts Group (.jpg, .jpeg, etc.), Portable NetworksGraphic (.png), or Tagged Image File Format (.tiff). In someembodiments, map tiles may be vector-based map tiles, encoded usingvector graphics, including, but not limited to, Scalable Vector Graphics(.svg) or a Drawing File (.drw). Embodiments may also include tiles witha combination of vector and raster data. Metadata or other informationpertaining to the map tile may also be included within or along with amap tile, providing further map service data to a client device. Invarious embodiments, a map tile may be encoded for transport utilizingvarious standards and/or protocols, some of which are described inexamples below.

In various embodiments, map tiles may be constructed from image data ofdifferent resolutions depending on zoom level. For instance, for lowzoom level (e.g., world or globe view), the resolution of map or imagedata need not be as high relative to the resolution at a high zoom level(e.g., city or street level). For example, when in a globe view, theremay be no need to render street level artifacts as such objects would beso small as to be negligible in many cases.

A map service may perform various techniques to analyze a map tilebefore encoding the tile for transport. This analysis may optimize mapservice performance for both client devices and a map service. In someembodiments map tiles may be analyzed for complexity, according tovector-based graphic techniques, and constructed utilizing complex andnon-complex layers. Map tiles may also be analyzed for common image dataor patterns that may be rendered as image textures and constructed byrelying on image masks. In some embodiments, raster-based image data ina map tile may contain certain mask values, which are associated withone or more textures. Embodiments may also analyze map tiles forspecified features that may be associated with certain map styles thatcontain style identifiers.

Other map services may generate map service data relying upon variousdata formats separate from a map tile. For example, map services thatprovide location data may utilize data formats conforming to locationservice protocols, such as, but not limited to, Radio Resource Locationservices Protocol (RRLP), TIA 801 for Code Division Multiple Access(CDMA), Radio Resource Control (RRC) position protocol, or LTEPositioning Protocol (LPP). Embodiments may also receive or request datafrom client devices identifying device capabilities or attributes (e.g.,hardware specifications or operating system version) or communicationcapabilities (e.g., device communication bandwidth as determined bywireless signal strength or wire or wireless network type).

A map service may obtain map service data from internal or externalsources. For example, satellite imagery used in map image data may beobtained from external services, or internal systems, storage devices,or nodes. Other examples may include, but are not limited to, GPSassistance servers, wireless network coverage databases, business orpersonal directories, weather data, government information (e.g.,construction updates or road name changes), or traffic reports. Someembodiments of a map service may update map service data (e.g., wirelessnetwork coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client devicerequests for map services. These requests may be a request for aspecific map or portion of a map. Embodiments may format requests for amap as requests for certain map tiles. In some embodiments, requests mayalso supply the map service with starting locations (or currentlocations) and destination locations for a route calculation. A clientdevice may also request map service rendering information, such as maptextures or stylesheets. In at least some embodiments, requests may alsobe one of a series of requests implementing turn-by-turn navigation.Requests for other geographic data may include, but are not limited to,current location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

A map service may, in some embodiments, may analyze client devicerequests to optimize a device or map service operation. For example, amap service may recognize that the location of a client device is in anarea of poor communications (e.g., weak wireless signal) and send moremap service data to supply a client device in the event of loss incommunication or send instructions to utilize different client hardware(e.g., orientation sensors) or software (e.g., utilize wireless locationservices or Wi-Fi positioning instead of GPS-based services). In anotherexample, a map service may analyze a client device request forvector-based map image data and determine that raster-based map databetter optimizes the map image data according to the image's complexity.Embodiments of other map services may perform similar analysis on clientdevice requests and as such the above examples are not intended to belimiting.

Various embodiments of client devices (e.g., client devices 902 a-902 c)may be implemented on different device types. Examples of aportable-multifunction device include the devices illustrated in FIGS. 1through 3 and 9, such as multifunction device 100 and multifunctiondevice 300. Client devices 902 a-902 c may utilize map service 930through various communication methods and protocols described below. Insome embodiments, client devices 902 a-902 c may obtain map service datafrom map service 930. Client devices 902 a-902 c may request or receivemap service data. Client devices 902 a-902 c may then process mapservice data (e.g., render and/or display the data) and may send thedata to another software or hardware module on the device or to anexternal device or system.

A client device may, according to some embodiments, implement techniquesto render and/or display maps. These maps may be requested or receivedin various formats, such as map tiles described above. A client devicemay render a map in two-dimensional or three-dimensional views. Someembodiments of a client device may display a rendered map and allow auser, system, or device providing input to manipulate a virtual camerain the map, changing the map display according to the virtual camera'sposition, orientation, and field-of-view. Various forms and inputdevices may be implemented to manipulate a virtual camera. In someembodiments, touch input, through certain single or combination gestures(e.g., touch-and-hold or a swipe) may manipulate the virtual camera.Other embodiments may allow manipulation of the device's physicallocation to manipulate a virtual camera. For example, a client devicemay be tilted up from its current position to manipulate the virtualcamera to rotate up. In another example, a client device may be tiltedforward from its current position to move the virtual camera forward.Other input devices to the client device may be implemented including,but not limited to, auditory input (e.g., spoken words), a physicalkeyboard, mouse, and/or a joystick.

Embodiments may provide various visual feedback to virtual cameramanipulations, such as displaying an animation of possible virtualcamera manipulations when transitioning from two-dimensional map viewsto three-dimensional map views. Embodiments may also allow input toselect a map feature or object (e.g., a building) and highlight theobject, producing a blur effect that maintains the virtual camera'sperception of three-dimensional space.

In some embodiments, a client device may implement a navigation system(e.g., turn-by-turn navigation). A navigation system provides directionsor route information, which may be displayed to a user. Embodiments of aclient device may request directions or a route calculation from a mapservice. A client device may receive map image data and route data froma map service. In some embodiments, a client device may implement aturn-by-turn navigation system, which provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as Global Positioning Satellite (GPS). A client device may displaymap image data that reflects the current location of the client deviceand update the map image data in real-time. A navigation system mayprovide auditory or visual directions to follow a certain route.

A virtual camera may be implemented to manipulate navigation map dataaccording to some embodiments. Some embodiments of client devices mayallow the device to adjust the virtual camera display orientation tobias toward the route destination. Embodiments may also allow virtualcamera to navigation turns simulating the inertial motion of the virtualcamera.

Client devices may implement various techniques to utilize map servicedata from map service. Embodiments may implement some techniques tooptimize rendering of two-dimensional and three-dimensional map imagedata. In some embodiments, a client device may locally store renderinginformation. For example, a client may store a stylesheet which providesrendering directions for image data containing style identifiers. Inanother example, common image textures may be stored to decrease theamount of map image data transferred from a map service. Client devicesmay also implement various modeling techniques to render two-dimensionaland three-dimensional map image data, examples of which include, but arenot limited to: generating three-dimensional buildings out oftwo-dimensional building footprint data; modeling two-dimensional andthree-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data. Some embodiments ofclient devices may also order or prioritize map service data in certaintechniques. For example, a client device may detect the motion orvelocity of a virtual camera, which if exceeding certain thresholdvalues, lower-detail image data will be loaded and rendered of certainareas. Other examples include: rendering vector-based curves as a seriesof points, preloading map image data for areas of poor communicationwith a map service, adapting textures based on display zoom level, orrendering map image data according to complexity.

In some embodiments, client devices may communicate utilizing variousdata formats separate from a map tile. For example, some client devicesmay implement Assisted Global Positioning Satellites (A-GPS) andcommunicate with location services that utilize data formats conformingto location service protocols, such as, but not limited to, RadioResource Location services Protocol (RRLP), TIA 801 for Code DivisionMultiple Access (CDMA), Radio Resource Control (RRC) position protocol,or LTE Positioning Protocol (LPP). Client devices may also receive GPSsignals directly. Embodiments may also send data, with or withoutsolicitation from a map service, identifying the client device'scapabilities or attributes (e.g., hardware specifications or operatingsystem version) or communication capabilities (e.g., devicecommunication bandwidth as determined by wireless signal strength orwire or wireless network type).

FIG. 9 illustrates one possible embodiment of an operating environment900 for a map service 930 and client devices 902 a-902 c. In someembodiments, devices 902 a, 902 b, and 902 c can communicate over one ormore wire or wireless networks 910. For example, wireless network 910,such as a cellular network, can communicate with a wide area network(WAN) 920, such as the Internet, by use of gateway 914. A gateway 914may provide a packet oriented mobile data service, such as GeneralPacket Radio Service (GPRS), or other mobile data service allowingwireless networks to transmit data to other networks, such as wide areanetwork 920. Likewise, access device 912 (e.g., IEEE 802.11g wirelessaccess device) can provide communication access to WAN 920. Devices 902a and 902 b can be any portable electronic or computing device capableof communicating with a map service, such as a portable multifunctiondevice described below with respect to FIGS. 1 to 3 and 9. Device 902 ccan be any non-portable electronic or computing device capable ofcommunicating with a map service, such as a system described below inFIG. 9.

In some embodiments, both voice and data communications can beestablished over wireless network 910 and access device 912. Forexample, device 902 a can place and receive phone calls (e.g., usingvoice over Internet Protocol (VoIP) protocols), send and receive e-mailmessages (e.g., using Simple Mail Transfer Protocol (SMTP) or PostOffice Protocol 3 (POP3)), and retrieve electronic documents and/orstreams, such as web pages, photographs, and videos, over wirelessnetwork 910, gateway 914, and WAN 920 (e.g., using Transmission ControlProtocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)).Likewise, in some implementations, devices 902 b and 902 c can place andreceive phone calls, send and receive e-mail messages, and retrieveelectronic documents over access device 912 and WAN 920. In variousembodiments, any of the illustrated client device may communicate withmap service 930 and/or other service(s) 950 using a persistentconnection established in accordance with one or more securityprotocols, such as the Secure Sockets Layer (SSL) protocol or theTransport Layer Security (TLS) protocol.

Devices 902 a and 902 b can also establish communications by othermeans. For example, wireless device 902 a can communicate with otherwireless devices (e.g., other devices 902 a or 902 b, cell phones) overthe wireless network 910. Likewise devices 902 a and 902 b can establishpeer-to-peer communications 942 (e.g., a personal area network) by useof one or more communication subsystems, such as Bluetooth®communication from Bluetooth Special Interest Group, Inc. of Kirkland,Wash. 902 c can also establish peer to peer communications with devices902 a or 902 b. (not pictured). Other communication protocols andtopologies can also be implemented. Devices 902 a and 902 b may alsoreceive Global Positioning Satellite (GPS) signals from GPS 940.

Devices 902 a, 902 b, and 902 c can communicate with map service 930over the one or more wire and/or wireless networks, 910 or 912. Forexample, map service 930 can provide a map service data to renderingdevices 902 a, 902 b, and 902 c. Map service 930 may also communicatewith other services 950 to obtain data to implement map services. Mapservice 930 and other services 950 may also receive GPS signals from GPS940.

In various embodiments, map service 930 and/or other service(s) 950 maybe configured to process search requests from any of client devices.Search requests may include but are not limited to queries for business,address, residential locations, points of interest, or some combinationthereof. Map service 930 and/or other service(s) 950 may be configuredto return results related to a variety of parameters including but notlimited to a location entered into an address bar or other text entryfield (including abbreviations and/or other shorthand notation), acurrent map view (e.g., user may be viewing one location on themultifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriainclude but not limited to a quantity of times the search result (e.g.,a particular point of interest) has been requested, a measure of qualityassociated with the search result (e.g., highest user or editorialreview rating), and/or the volume of reviews for the search results(e.g., the number of times the search result has been review or rated).

In various embodiments, map service 930 and/or other service(s) 950 maybe configured to provide auto-complete search results that may bedisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the internet) by map service 930 and/or other service(s) 950,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device may be configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 930 and/or other service(s) 950 mayprovide one or more feedback mechanisms to receive feedback from clientdevices 902 a-c. For instance, client devices may provide feedback onsearch results to map service 930 and/or other service(s) 950 (e.g.,feedback specifying ratings, reviews, temporary or permanent businessclosures, errors etc.); this feedback may be used to update informationabout points of interest in order to provide more accurate or moreup-to-date search results in the future. In some embodiments, mapservice 930 and/or other service(s) 950 may provide testing informationto the client device (e.g., an A/B test) to determine which searchresults are best. For instance, at random intervals, the client devicemay receive and present two search results to a user and allow the userto indicate the best result. The client device may report the testresults to map service 930 and/or other service(s) 950 to improve futuresearch results based on the chosen testing technique, such as an A/Btest technique in which a baseline control sample is compared to avariety of single-variable test samples in order to improve results.

Example Mapping Functionality

FIG. 3 illustrates another example of a multifunction device that mayimplement a map tool in accord with the embodiments described, where themultifunction device may be configured in a manner similar to themultifunction device described above. In the illustrated embodiment, amultifunction device 300 includes a mapping application (e.g., mapmodule 154 described above) that may be stored in one or more memoriesof multifunction device 300 and executed on one or more processors ofmultifunction device 300. As is the case for the multifunction devicedescribed above, multifunction device 300 may include one or morecontrols 302 for operating the multifunction device. These controls mayinclude but are not limited to power controls for turning the device onand off, volume controls for adjusting the ear piece volume or thespeaker volume, menu controls for navigation functions of the device,and function controls for initiating one or more function or actions onthe device. Controls 302 may include hardware controls or softwarecontrols. For instance, the bottom left corner of electronic display 312includes a graphical representation of a control 312 that may beselected by a user, such as by way of touch in accordance with the touchscreen functionality described above.

Multifunction device 300 may also include other components similar tothose described above, such as a microphone 304, an earpiece 306 (e.g.,a speaker through which to convey audio representations of telephonecalls), an optical sensor 308, and/or a speaker 310. Each of thesecomponents may be configured in a similar manner to those like-namedcomponents of FIG. 2 described above. Furthermore, electronic display312 may be configured with touch screen capability, such as touch screen112 described above. In various embodiments, controls (e.g., on screencontrol(s) 302) may be utilized to perform any of a variety ofmap-related functions including but not limited to zoom in, zoom out,rotate screen, pan screen, toggle views (e.g., two-dimensions to threedimensions and vice versa), and/or another map related activity. Invarious embodiments, one or more gestures may be utilized to perform anyof the aforesaid map controls (with or without the use of an actualgraphical on-screen control). In one non-limiting example, a one figuregesture may be utilized to adjust the pitch within a three-dimensionalmap view.

As noted above, multifunction device 300 includes a mapping applicationthat may be stored in one or more memories of multifunction device 300and executed on one or more processors of multifunction device 300. Inthe illustrated embodiment, the graphical representation of the mappingapplication may include a map 314 of a geographic region. This map maybe presented as a two-dimensional map or a three-dimensional map, theselection of which may be specified through, e.g., a user-configurableparameter of the mapping application. In some embodiments, themultifunction device may toggle between two-dimensional map orthree-dimensional map views responsive to input from any input componentof the multifunction device. In one non-limiting example, input fromorientation sensor(s) 168 may initiate the transition from atwo-dimensional map view to a three-dimensional map, and vice versa. Forinstance, one or more of orientation sensor(s) 168 may detect a tilt(e.g., a user-initiated tilt) in the orientation of the multifunctiondevice and, in response, initiate the aforesaid toggling.

Map 314 may include a graphical position indicator 316, which mayrepresent the location of the multifunction device within the geographicregion of the map. Generally position indicator 316 may represent thecurrent or real-time position of the multifunction device, although itshould be understood that in some cases there may exist some smallamount of temporal latency between the actual position of themultifunction device and the graphical representation of that location(e.g., position indicator 316). This may occur, e.g., when themultifunction device is in motion. In various embodiments, themultifunction device may be configured to perform map matching includingbut not limited to aligning a sequence of observed user positions with aroad network on a digital map. In various embodiments, the multifunctiondevice may be configured to perform a “snap to” function in which thegraphical position indicator 316 is aligned onto a roadway when theuser's position falls within in a specified threshold distance of theroadway.

Furthermore, multifunction device 300 may generally be operated by auser. For example, multifunction device 300 may in some cases be asmartphone utilized by an individual to make phone calls, send textmessages, browse the internet, etc. As use of multifunction device by anindividual generally implies the individual is proximate to themultifunction device (e.g., the user may be holding the device in his orher hand), references herein to the location of the device and thelocation of the user may be considered to be synonymous. However, itshould be understood that in some cases the actual position of themultifunction device and the user of that device may differ by somedistance. For instance, the user may place his or her multifunctiondevice on a table of an outdoor café while sitting in a nearby chair. Inthis case, the position of the device and the position of the user maydiffer by some small amount. In another example, multifunction device300 may be mounted on a car dashboard (e.g., for use as a navigationdevice) while the user of the device sits nearby (e.g., in the driverseat of the car). In this case as well, the position of the device andthe position of the user may differ by some small amount. Despite thesesmall differences in position, generally the position of themultifunction device and the position of the multifunction device usermay be considered to coincide.

In various embodiments, the map 314 displayed by the multifunctiondevice may include one or more roads (e.g., roads 318 a-b), buildings(not illustrated), terrain features (e.g., hills, mountains) (notillustrated), parks (not illustrated), water bodies (not illustrated),and/or any other item that may be conveyed by a map. In some cases, themap may also include other map or navigation information including butlimited to readouts from one or more of a directional compass, analtimeter, and/or a thermometer.

In various embodiments, the mapping application may be configured togenerate directions from an origination (e.g., an address or a user'scurrent position) to a destination (e.g., an address, landmark,bookmarked/saved location, or point of interest). For instance, anindication of the origination and/or destination may be input into themulti function device by the user. The multifunction device may generateone or more candidate routes between those two points. The multifunctiondevice may select one of those routes for display on the device. Inother cases, multiple candidate routes may be presented to the user andthe user may select a preferred route. In the illustrated embodiment,one route is illustrated as route 320. The route may also includeturn-by-turn directions which may be presented to the user (in 2D or3D), such as a graphical indication to perform a turn 322 a from road318 a to road 318 b. In some embodiments, this graphical indication toperform a turn may be supplemented or substituted with an audibleindication to turn, such as a voice command from speaker 310 thatindicates the user is to “turn left in 100 yards,” for example. In someembodiments, the route that is selected may be presented to the user asa route overview. For instance, before proceeding with navigation, themultifunction device may generate a route overview display thatgraphically indicates key information for the route, such as key turns,route distance and/or an estimated time for traversing the route. Insome cases, the multifunction device may be configured to generate adisplay of driving maneuvers (e.g., turns, lane changes, etc.) thatoccur in quick succession, either in the route overview or during actualnavigation. This information may help the user safely prepare for suchmaneuvers. In some cases, the route information may be presented in alist format, such as a list of turns or other maneuvers.

In various embodiments, the mapping application of the multifunctiondevice may be configured to track the position of the user over time andcorrespondingly adjust the graphical position indicator 316 to indicatethe new position. For instance, the mapping application may determinethat the user is traveling along route 320 from position information(e.g., information from GPS module 135) and update the map 314accordingly. For instance, in some cases the map 314 may remainstationary while position indicator 316 is moved along the route. Inother cases, position indicator 316 may remain stationary or “fixed”while map 314 is moved (e.g., panned, turned, etc.) around the positionindicator.

In various embodiments, the multifunction device may be configured todisplay alternate or contingency routes. In some cases, these routes maybe selectable by the user (e.g., via the touch screen interface). Inother cases, the multifunction device may select a best route based onone or more parameters, such as shortest distance or time. In somecases, these parameters or preferences may be set by the user.

As described in more detail below, the multifunction device may invarious embodiments receive routing information that specifies a routefrom a map service. In some case, the multifunction device may carry outnavigation guidance in accordance with this route. However, in somecases, the multifunction device may perform a reroute operation in orderto generate a new route to the destination. For instance, the user mayhave deviated from the original route or explicitly requested a newroute. In some cases, the multifunction device may perform reroutingbased on cached map data stored on the multifunction device.

In various embodiments, the multifunction device may be configured toperform route correction based on real-time data, such as updates in mapinformation, road conditions, traffic conditions, and/or weatherconditions. For instance, the multifunction device may be configured toalter a route such that the route avoids a construction zone or adangerous storm cell.

In various embodiments, the multifunction device may be configured toperform lane guidance independently or as part of navigation guidance.For instance, the multifunction device may, in response to detectingthat multiple turns follow in quick succession, provide the user with adirection or suggestion as to which lane to occupy. For instance, avoice or visual indication may specify that the user “turn right, thenmove to the left lane” in anticipation of a subsequent left turn. Inanother example, the multifunction device may detect one or more laneclosures (e.g., due to construction or other reasons) and instruct theuser to avoid such lanes.

In various embodiments, the multifunction device may be configured togenerate voice prompts for directions. For instance, during navigationguidance, the multifunction device may be configured to generate audiorepresentations of the next turn or driving maneuver on the route. Forinstance, the multifunction device may be configured to audibly indicatethe user should “turn left in 100 yards” or some other audibleindication of a maneuver.

In various embodiments, the multifunction device may be responsive tovarious voice commands for performing actions including a command toobtain a route. For instance, the multifunction device may interpret theuser's voice through a microphone or other transducer of themultifunction device. The user may specify an origination and adestination for the requested route. In various embodiments, themultifunction device may be configured to utilize the user's currentlocation as the origination for the route.

In various embodiments, the multifunction device may be configured toperform a search along a specific route, such as current navigationroute. For instance, the user of the multifunction device may requestthe location of points of interest, such as fuel stations orrestaurants. However, if a user is traveling along a particular route,they may not be particularly interested in points of interest that arenot proximate to that route. As such, the multifunction device may beconfigured to scope any searches to points of interested within aspecified distance away from the route. In various embodiments, thisdistance may be a configurable parameter.

In various embodiments, the multifunction device may be configured todisplay various graphical layers including but not limited to agraphical map information, aerial images (e.g., satellite-acquiredimages), and/or traffic information. For instance, in the trafficinformation example, the multifunction device may overlay color codedtraffic information on roadways to indicate the speed at which trafficis flowing. For example, green color coding may be used to indicatetraffic is flowing normally, and yellow or red may be used to indicatetraffic slowdowns.

In various embodiments, the multifunction device may be configured todisplay any quantity of metrics or statistics about a navigation routeincluding but not limited to an estimated time of arrival, traveldistance remaining, average speed (overall or moving average), topspeed, and/or other route statistics.

In various embodiments, the multifunction device may be configured todisplay routes at different angles in order to accommodate thepreferences of different users. Such viewing angles may include a birdseye view for two-dimensional maps to any of a variety of camera anglesavailable for a three-dimensional map.

In various embodiments, the multifunction device may be configured toprovide navigation information other than map and routing information.For instance the multifunction device may expose output from any of thehardware device described above with respect to FIG. 1. In onenon-limiting example, an orientation sensor 168 may include a compassthat outputs direction data. The multifunction device described hereinmay be configured to display this directional data as a virtual compass,for example.

Map Tool

FIGS. 4A-4E are flowcharts depicting selected processing stages ofembodiments of a map tool as implemented within a mapping application.The mapping application, as discussed above, may be invoked through thea user selecting the mapping application through the interface of amultifunction device 300. The mapping application may engage theservices of the map service operating system as described in regard toFIG. 9.

As per FIG. 4A, in some embodiments, a map tool, given multiple datasets of mapping information corresponding to a map or map area, mayconstruct a three-dimensional model on which to base a map view todisplay. As reflected in stage 402, the map tool may receive two or moredata sets of mapping information corresponding to a map region. In somecases, the mapping information is vector data and not raster image data.

Based on the received two or more data sets of mapping information, themap tool may determine one or more spatial dimensions for one or moreobjects in the map region, as reflected in stage 404. For example, themap tool may receive three-dimensional mapping information for the mapregion from map service 930 or from GPS 940. The map tool may alsoreceive, from map service 930 or service 950 for example,two-dimensional mapping information that includes footprint informationfor buildings within the map region for which the three-dimensionalmapping information corresponds.

The footprint information may include the location and dimensions of thephysical boundaries of a given building within the map area. Forexample, in a simple case of a square building, the footprint mayspecify the locations of each corner of the building along with thelength of each side of the building. In this example, if the squarebuilding has two stories and a flat roof, a simple cube may provide anaccurate representation of the volume and dimensions occupied by thebuilding within the map region. Further, as described above, a depictionof a simple cube may provide a more efficiently usable map view. Whilethe footprint in this example is a simple square, in general, the maptool may operate on any shape of footprint. Further, the footprint maybe the footprint of any object within the map region.

Given a footprint and the area of the map region in which the footprintexists, and given three-dimensional information corresponding to the mapregion, the map tool may determine one or more height values for thefootprint. The map tool may use one or more points within the footprint,or points proximate to the footprint, and correlate the one or morepoints to respective one or more height values from thethree-dimensional mapping information, where each respective heightvalue corresponds to a respective point. In this way, the map tool maydetermine a height value for each of the points in the footprint. Aresult is that the map tool, based on two different data sets of mappinginformation, determines one or more spatial dimensions for one or moreobjects in the map region, as reflected in stage 404. In this example,spatial dimensions are determined from the two-dimensional mappinginformation (footprints) and spatial dimensions are determined from thethree-dimensional mapping information (height values).

In some embodiments, a footprint may be divided into multiple regions,and height values may be correlated to the three-dimensional informationfor one or more locations within each of the regions. For example, abuilding may be L-shaped, where one leg of the L is not as tall as theother leg of the L. In this case, the footprint may be divided into tworegions, one region corresponding to each leg of the L, and a heightvalue for each region may be used as the basis for extruding thefootprint into three dimensional space. The regions of the footprint maybe determined in other manners, such as uniform division of thefootprint into any given number of regions, for example, dividing eachfootprint into quarters.

Once the map tool has identified one or more height values correspondingto one or more points in a given footprint, the map tool may generate athree-dimensional version of the footprint. The map tool may generate anentire three-dimensional model based on the three-dimensional versionsof each object footprint in the map region, as reflected in stage 406.For example, the map tool may extrude or extend the object footprintinto three-dimensional space based on the height value. The generatedthree-dimensional model has a higher level of granularity than thetwo-dimensional mapping information in that the three-dimensional modelincludes height values in addition to the footprint information. Thegenerated three-dimensional model also has a lower level of granularitythan the three-dimensional mapping information in that thethree-dimensional model does not have as much detail regarding thedimensions of objects within the map region. In other words, in thisexample, the generated three-dimensional model has a different level ofgranularity from each of the sets of mapping information on which thethree-dimensional model is based.

The generated three-dimensional model may then serve as the basis forthe generation of a display of the map area such as the map view inFIGS. 5A and 5B, as reflected in stage 408. In some cases, thethree-dimensional model may be augmented to include additional details,such as texture and shading for one or more objects within thethree-dimensional model, or doors or windows or outlines of doors orwindows. The additional details may be extracted from the mappinginformation already used, or the additional details may be based onanother source of mapping information. For example, the map tool may usethe cardinal direction of the user with respect to the current positionof the sun to add accurate shading information to objects within thethree-dimensional model. In other cases, the map tool may access adefault settings file to apply default textures to various objects suchas buildings or streets.

As discussed above, a simplified map view may provide a user with a moreefficient map using experience. FIGS. 5A and 5B provide two differentmap views using the map tool, where FIG. 5A presents a ground levelvirtual camera viewpoint or perspective and FIG. 5B provides a bird'seye virtual camera viewpoint or perspective. FIG. 5A may include labelssuch as labels 510, 512, and 514, and buildings 506, 508, 520, 530, 532,and 534. In some cases, buildings may have different shape such asbuilding 520. In some cases, the map view may include additional objectssuch as tree 502, fountain 534, or user 518. Overall, withoutdistractions such as advertisements, vehicles, or people, the simplifiedmap view is easier to comprehend and easier to navigate.

FIGS. 5C and 5D depict two versions of a map view of the same map areaas depicted within screen area 312 of a mobile device. FIG. 5C depicts araster version of the map area. The depiction in FIG. 5C may be from araster image taken, for example, from a satellite or helicopter. Thephotographic detail may provide a user with a general impression of themap area. However, with respect to navigation, a user may find thebuilding details and cars a distraction. By contrast, the map view inFIG. 5D, based on a generated three-dimensional model, is aestheticallycleaner and simpler, and as a consequence, the street and buildingimages are easier to visually process. While some visual details arelost, the gain in the ease of identifying streets and buildings may be apreferable outcome to a user more interested in navigating than in theshape of a roof or how many air conditioning units are on a given roof.In some embodiments, when the two-dimensional mapping informationdiscussed above indicates a green space such as a park, the map tool maydisplay a flat area without buildings, such as area 550 in FIG. 5D.Further, in some cases, area 550 may be colored to indicate that thearea is a green space, or area 550 may be colored blue to indicate thatthe area is a body of water.

As per FIG. 4B, in some embodiments, a map tool may receive inputindicating a location in a map, as reflected in stage 422. For example,a user of multifunction device 300 or a user at a desktop computer mayenter an address or otherwise indicate a certain location, such asAustin Children's Museum or the corner of Sixth Street and CongressAvenue.

Given a location in a map, the map tool may receive or requesttwo-dimensional mapping information for the map, as reflected in stage424. For example, the map tool may receive or request from Map Service930 mapping information including footprints for objects within the areaindicated through the location in the map.

Given the location in the map, the map tool may also receive or requestheight information for the map, as reflected in stage 426. For example,the map tool may receive or request from Map Service 930 mappinginformation that includes height values for various objects within thearea indicated through the location in the map. The mapping information,as in the example discussed above in regard to FIG. 4A, may be vectordata instead of raster data.

The map tool may then, similar to the process described above in regardto FIG. 4A, correlate a location or point in the footprint of an objectin the map region with a height value from the height information. Insome cases, one or more points in or proximate to the footprint may becorrelated to respective height values in the height information. Forexample, height values for each corner of the footprint, or a pointsalong the perimeter, or only a single height value for somewhere nearthe center of the footprint. In some cases, given multiple points withinthe footprint, the map tool may select the highest height value from therespective, corresponding height values. In other cases, the map toolmay calculate an average height value from the multiple height valuescorresponding to the respective points in the footprint. In other cases,the height and top of the extruded footprint may be created through thecreation of a surface connecting each of different height values withina given footprint.

Similar to the creation of a three-dimensional model described above inregard to FIG. 4A, the map tool may render a three-dimensionalrepresentations of the objects based on the height information, wherethe rendering includes extruding a respective footprint for each objectto create a respective three-dimensional version of the object throughthe addition of a height value, or height values, or a height valuebased on multiple height values, as reflected in stage 428. In somecases, the map tool may represent the collection of extruded footprintswithin a data structure storing the defining information for each of theextruded footprints, in addition to information for where within the mapregion the given extruded footprint exists.

Given a rendering of each extruded footprint, which is athree-dimensional object, the map tool may display a three-dimensionalversion of the three-dimensional object in a view of the map region, asreflected in stage 430. Upon displaying each of the generatedthree-dimensional objects, a user may see a version of the map regionthat is a simplified version of the map region, as compared to araster-based map view or a photo-realistic version of the map region.

As per FIG. 4C, in some embodiments, the map tool may receive or requesttwo-dimensional mapping information for a map or map region, where thetwo-dimensional mapping information includes a footprint for an object,as reflected in stage 442. The map tool may also receive or requestthree-dimensional mapping information for the map region, such as meshdata from Map Service 930, where the three-dimensional mappinginformation includes multiple height values corresponding to one or morelocations in the map, as reflected in stage 444.

Given the two different kinds of mapping information, the map tool maycorrelate a given location of the footprint of the object with arespective height value from the multiple height values in thethree-dimensional mapping information, as reflected in stage 446. Inorder for the correlation between the locations in the two-dimensionalmapping information to height values in the three-dimensional mappinginformation to be valid, both sets of mapping information depict ordescribe an overlapping area of the map or map region.

Given a footprint for an object and at least one height valuecorresponding to the footprint, the map tool may extrude the footprint,based on the height value, to create a three-dimensional version of theobject, as reflected in stage 448. The map tool may then display thethree-dimensional version of the object, as reflected in stage 450. Inthe general case, the map tool may perform repeat the correlating andextruding processes for each footprint in the map region in order todisplay a complete three-dimensional view of the map region.

As per FIG. 4D, in some embodiments, the map tool may begin with thecreation of a representation of map area, where the representation isdivided into segments defined in terms of two-dimensional space, asreflected in stage 462. For example, the map area may correspond to a200 square meter area, and each segment may be defined to correspond toa square meter. In other cases, segments may be defined in terms ofother shapes.

The map tool may then request or receive three-dimensional mappinginformation for the map, where the three-dimensional mapping informationincludes height values corresponding to at least one point in eachsegment location, as reflected in stage 464. The map tool may thencorrelate a respective height value for each of the segments, asreflected in stage 466. In some cases, for a given segment, the map toolmay correlate a height value from the center of the segment and for apoint along each side of the segment.

Given the segments and respective height values, the map tool maygenerate a three-dimensional version of the segment through the additionof a respective height value to a respective segment, as reflected instage 468. In this way, the map tool creates an extruded,three-dimensional version of the two-dimensional segment. This processmay be repeated for each segment, as reflected in stage 470.

At this point, the map tool has generated a model with multiple segmentsof varying heights and may display a three-dimensional view of the mapbased on the model, as reflected in stage 472. If each of the segmentsis displayed as defined within the model, the result may be a mesh-likedisplay of segments with lines bounding each segment. Therefore, in somecases, the map tool may smooth the segments, for example, if the heightdifference between adjacent segments is zero, small, or within athreshold value, then the map tool may merge the segments into onesegment such that each adjacent side of the individual segments become asingle surface. This process may be repeated for each segment in themodel and the result would be similar to the result produced by theembodiment described above in regard to FIGS. 4A and 4B.

Given a map view based on the generated three-dimensional model, the maptool may receive input corresponding to a navigation operation or to achange in virtual camera viewpoint. For example, a user may wish to see,given a display of a building within a map view, the view from the otherside of the building. In such a case, through a finger swipe, othergesture on a touch-sensitive screen, the map tool may update the mapview in response to the user input. Further, given that the modelinformation already exists within the model, the model does not need tobe regenerated, meaning that no new mapping information is needed toprovided the user with a new view of the map area.

In some embodiments, only footprints are subdivided into segments, andthe after the map tool performs the above-described smoothing/mergingoperation, the resulting three-dimensional version of the footprint mayhave a more accurate representation of the top of the building sinceeach of the tops of each segments would have been smoothed together intoone surface.

In some embodiments, a map view is updated as the user and multifunctiondevice change positions or as a user on a desktop computer navigateswithin a map view. In such a case, the map view may be updated based ona combination of an already computed three-dimensional model augmentedwith computed model information for the new area displayed in the map asa result of the change in location. In this way, in this case, acomplete recalculation of the 3D model is avoided, and only the area ofthe map that is new is used to augment the already generated 3D model.

In some cases, based on a projection of where the user is going, the maptool may prefetch corresponding mapping information, and if theprojection is wrong or partially wrong, some or all of the prefetchedmapping information may be discarded.

As per FIG. 4E, in some embodiments, the map tool may generate, based onmultiple data sets, a three-dimensional model of a map region includingmultiple three-dimensional objects, as reflected in stage 482. The maptool may generate the three-dimensional model according to any of theabove described method for generating a three-dimensional model withregard to FIGS. 4A-4D.

The map tool may then display a map view based on the three-dimensionalmodel, as reflected in stage 484. The map tool may, through aninterface, input indicating a selection of an object in thethree-dimensional model, as reflected in stage 486. In the case of amobile device, the interface may be a touch-sensitive display screen. Inthe case of a desktop computer, the interface may a window and the inputmay be a selection of an object displayed in the window. In either case,based on the input, the map tool determines an object in the displayedthree-dimensional model to select.

In some cases, given a map view, a user may adjust the virtual cameraperspective from which the map is drawn. For example, given aconstructed three-dimensional model as described, a user may viewdifferent sides of a building in the map view without using additionalmapping information and based solely on the already constructedthree-dimensional model.

Given a selected object, the map tool may invoke a function thatextracts data from one or more of the data sets of mapping informationfrom which the three-dimensional model was generated or from other datarelated to the map region, as reflected in stage 488. In some cases, theuser may choose to display additional information regarding the selectedobject. For example, on a mobile device, a user may tap and hold afinger over a displayed object in the map view, the map tool may thenprovide the user with various options, such as adding a label,displaying an already assigned label for the object, displayinginformation regarding businesses within the building, whether or not theselected object is a point of interest, whether or not the objectincludes a restroom, among other options. In the case that the user addsa label, the user may choose for the label to be shared and the labelinformation may be uploaded to Map Service 930 to be provided to otherusers. In some cases, the map tool may retrieve the additionalinformation from Map Service 930.

In some cases, Map Service 930 may provide information collected fromother users that have previously provided feedback or informationregarding the selected object. This crowdsourced information may includesuch things as ratings for a restaurant within the building, comments onthe cleanliness of a public restroom, or hours of operation of anybusinesses within the building.

In the case that the user selection may be satisfied based on thealready received mapping information, the map view may be updated basedon the specified function and data extracted from the mappinginformation data sets, as reflected in stage 488. For example, if theuser selects to display a selected building with greater texture detail,the map tool may extract the information from the multiple data setsdescribed above regarding stage 482. However, in other cases, asdescribed above, the map view may be updated based on information fromother data sources.

Map Tool Module

FIG. 6 illustrates an embodiment of a Map Tool Module 600. As notedabove, the Map Tool Module 600 may implemented a variety of differentembodiments of a map tool.

In some embodiments, Control Module 604 may receive Input 602, which maybe various types of mapping information, as described above with respectto FIGS. 4A-4E. Given the mapping information, Control Module 604 mayinvoke Model Generation Module 606 to generate a model of thesurrounding environment, according to various embodiments discussedabove.

Given a model of the surrounding environment, Control Module 604 mayinvoke User Interface Module 608 in response to various user inputsindicating, among other things, a selection of an object within a mapview, information for labeling an object in the map view, or requestingmore information or specific information regarding an object in the mapview. In some cases, depending on the input, Map Tool Module 600 maycommunicate with Map Service 930 through Map Information InterfaceModule 610 to request or receive mapping information.

Depending on the embodiment and current state, Control Module 604 mayprovide a display of a map view as Output 620.

Example Embodiment Client/Server Architecture

FIG. 7 depicts an illustration, according to one embodiment, of acomputing environment in which various devices implementing a map toolmay operate. The case of a portable multifunction device has beendiscussed above with regard to FIG. 3.

As another example discussed above, a user at a desktop machine mayenter any particular address of any given structure, or the user mayenter a coordinate, or the user may enter a landmark, or the user maysimply navigate to a given map location. Once the user arrives at a maplocation, the user may navigate as a user on a mobile device wouldnavigate. In this way, without moving, a user at a stationary machine,may navigate through a given map view such that the above-mentionedembodiments of a map tool may operate to present the user with a similarmap view as a mobile user would see.

Example Embodiment Cloud Computing Environment

FIG. 8 depicts one possible computing environment that includes a device810 accessing a cloud computing environment 804 over network 802. Inthis example, an installed application on a mobile device may be used toaccess any of the above-discussed embodiments of a map tool executingwithin one of the virtual computing instances 806 through 808.

In other embodiments, as discussed above in the case of a client/serverarchitecture, the map tool may be implemented on a computer 812accessing a cloud computing environment 804 over network 802. In thisexample, a user may log in to the cloud computing environment 804 toaccess a virtual computing instance within which an embodiment of themap tool is executing or may be executed.

Example Computer System

FIG. 10 illustrates computer system 9900 that may execute theembodiments discussed above. In different embodiments, the computersystem may be any of various types of devices, including, but notlimited to, a personal computer system, desktop computer, laptop,notebook, or netbook computer, mainframe computer system, handheldcomputer, workstation, network computer, a camera, a set top box, amobile device, a consumer device, video game console, handheld videogame device, application server, storage device, a television, a videorecording device, a peripheral device such as a switch, modem, router,or in general any type of computing or electronic device.

In one embodiment, computer system 9900 includes one or more processors9910 a-9910 n coupled to system memory 9920 via input/output (I/O)interface 9930. The computer system further includes network interface9940 coupled to I/O interface 9930, and one or more input/output devices9950, such as cursor control device 9960, keyboard 9970, and one or moredisplays 9980. In some embodiments, it is contemplated that embodimentsmay be implemented using a single instance of a computer system, whilein other embodiments may be implemented on multiple such systems, ormultiple nodes making up a computer system, may be configured to hostdifferent portions or instances of embodiments. For example, in oneembodiment some elements may be implemented via one or more nodes of thecomputer system that are distinct from those nodes implementing otherelements.

In various embodiments, the computer system may be a uniprocessor systemincluding one processor, or a multiprocessor system including severalprocessors (e.g., two, four, eight, or another suitable number). Theprocessors may be any suitable processor capable of executinginstructions. For example, in various embodiments, the processors may begeneral-purpose or embedded processors implementing any of a variety ofinstruction set architectures (ISAs), such as the x86, PowerPC, SPARC,or MIPS ISAs, or any other suitable ISA. In multiprocessor systems, eachof processors may commonly, but not necessarily, implement the same ISA.

In some embodiments, at least one processor may be a graphics processingunit. A graphics processing unit or GPU may be considered a dedicatedgraphics-rendering device for a personal computer, workstation, gameconsole or other computing or electronic device. Modern GPUs may be veryefficient at manipulating and displaying computer graphics, and theirhighly parallel structure may make them more effective than typical CPUsfor a range of complex graphical algorithms. For example, a graphicsprocessor may implement a number of graphics primitive operations in away that makes executing them much faster than drawing directly to thescreen with a host central processing unit (CPU). In variousembodiments, the content object processing methods disclosed herein may,at least in part, be implemented with program instructions configuredfor execution on one of, or parallel execution on two or more of, suchGPUs. The GPU(s) may implement one or more application programmerinterfaces (APIs) that permit programmers to invoke the functionality ofthe GPU(s). Suitable GPUs may be commercially available from vendorssuch as NVIDIA Corporation, ATI Technologies (AMD), and others.

System memory within the computer system may be configured to storeprogram instructions and/or data accessible from a processor. In variousembodiments, the system memory may be implemented using any suitablememory technology, such as static random access memory (SRAM),synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or anyother type of memory. In the illustrated embodiment, programinstructions and data may implement desired functions, such as thosedescribed above for the various embodiments are shown stored withinsystem memory 9920 as program instructions 9925 and data storage 9935,respectively. In other embodiments, program instructions and/or data maybe received, sent or stored upon different types of computer-accessiblemedia or on similar media separate from system memory or the computersystem. Generally, a computer-accessible medium may include storagemedia or memory media such as magnetic or optical media, e.g., disk orCD/DVD-ROM coupled to the computer system via the I/O interface. Programinstructions and data stored via a computer-accessible medium may betransmitted from transmission media or signals such as electrical,electromagnetic, or digital signals, which may be conveyed via acommunication medium such as a network and/or a wireless link, such asmay be implemented via the network interface.

In one embodiment, the I/O interface may be configured to coordinate I/Otraffic between the processor, the system memory, and any peripheraldevices in the device, including a network interface or other peripheralinterfaces, such as input/output devices. In some embodiments, the I/Ointerface may perform any necessary protocol, timing or other datatransformations to convert data signals from one component into a formatsuitable for another component to use. In some embodiments, the I/Ointerface may include support for devices attached through various typesof peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of the I/Ointerface may be split into two or more separate components, such as anorth bridge and a south bridge, for example. In addition, in someembodiments some or all of the functionality of the I/O interface, suchas an interface to system memory, may be incorporated directly into theprocessor.

The network interface of the computer system may be configured to allowdata to be exchanged between the computer system and other devicesattached to a network, such as other computer systems, or between nodesof the computer system. In various embodiments, the network interfacemay support communication via wired or wireless general data networks,such as any suitable type of Ethernet network, for example; viatelecommunications/telephony networks such as analog voice networks ordigital fiber communications networks; via storage area networks such asFibre Channel SANs, or via any other suitable type of network and/orprotocol.

The I/O devices may, in some embodiments, include one or more displayterminals, keyboards, keypads, touchpads, scanning devices, voice oroptical recognition devices, or any other devices suitable for enteringor retrieving data from one or more computer systems. Multiple I/Odevices may be present in the computer system or may be distributed onvarious nodes of the computer system. In some embodiments, similar I/Odevices may be separate from the computer system and may interact withone or more nodes of the computer system through a wired or wirelessconnection, such as over the network interface.

The memory within the computer system may include program instructionsconfigured to implement each of the embodiments described herein. In oneembodiment, the program instructions may include software elements ofembodiments of the modules discussed earlier. The data storage withinthe computer system may include data that may be used in otherembodiments. In these other embodiments, other or different softwareelements and data may be included.

Those skilled in the art will appreciate that the computer system ismerely illustrative and is not intended to limit the scope of theembodiments described herein. In particular, the computer system anddevices may include any combination of hardware or software that canperform the indicated functions, including a computer, personal computersystem, desktop computer, laptop, notebook, or netbook computer,mainframe computer system, handheld computer, workstation, networkcomputer, a camera, a set top box, a mobile device, network device,internet appliance, PDA, wireless phones, pagers, a consumer device,video game console, handheld video game device, application server,storage device, a peripheral device such as a switch, modem, router, orin general any type of computing or electronic device. The computersystem may also be connected to other devices that are not illustrated,or instead may operate as a stand-alone system. In addition, thefunctionality depicted within the illustrated components may in someembodiments be combined in fewer components or distributed in additionalcomponents. Similarly, in some embodiments, the functionality of some ofthe illustrated components may not be provided and/or other additionalfunctionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read from anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from the computer system may be transmitted via transmissionmedia or signals such as electrical, electromagnetic, or digitalsignals, conveyed via a communication medium such as a network and/or awireless link. Various embodiments may further include receiving,sending or storing instructions and/or data implemented in accordancewith the foregoing description upon a computer-accessible medium.Accordingly, the present invention may be practiced with other computersystem configurations.

CONCLUSION

Various embodiments may further include receiving, sending or storinginstructions and/or data implemented in accordance with the foregoingdescription upon a computer-accessible medium. Generally, acomputer-accessible medium may include storage media or memory mediasuch as magnetic or optical media such as disks or DVD/CD-ROM, volatileor non-volatile media such as RAM, ROM, flash drives, as well astransmission media or signals such as electrical, electromagnetic, ordigital signals, conveyed via a communication medium such as networkand/or a wireless link.

The various methods described herein represent example embodiments ofmethods. These methods may be implemented in software, hardware, orthrough a combination of hardware and software. The order of the methodsteps may be changed, and various elements may be added, reordered,combined, omitted, or modified.

Various modifications and changes may be made as would be obvious to aperson skilled in the art having the benefit of this disclosure. It isintended that the invention embrace all such modifications and changesand, accordingly, the above description to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A method, comprising: performing, by one or morecomputing devices of a portable electronic device: receiving inputcorresponding to a navigation operation for a map view of the portableelectronic device, wherein the input indicates a location in a map;receiving two-dimensional mapping information for the map, wherein thetwo-dimensional mapping information includes a respective footprint forone or more objects; receiving three-dimensional mapping informationcomprising three-dimensional mesh data for the one or more objects,wherein the three-dimensional mesh data comprises height information forthe one or more objects, and wherein the height information includesheight values corresponding to one or more locations in the map;rendering three-dimensional representations of the one or more objectsbased on the height information, wherein said rendering comprisesextruding the respective footprint of each given object of the one ormore objects to create a respective three-dimensional version of thegiven object; and displaying the map view of the location including thethree-dimensional representations of each of the one or more objects;wherein the map view is updated based on the created three-dimensionalversion of the one or more objects augmented with computed modelinformation for a new area displayed in the map view as a result of themap view being updated.
 2. The method of claim 1, further comprising:correlating a location of the footprint of the object in thetwo-dimensional mapping information with a height value from heightinformation; and correlating another location of the footprint of theobject with another height value from the height information.
 3. Themethod of claim 1, further comprising: identifying two or more regionsof a footprint based on a similarity of height values corresponding toeach respective region of the two or more regions, wherein the footprintcorresponds to an object of the one or more objects; and dividing, basedon the two or more regions, the footprint into the two or more regions;wherein said extruding the respective footprint of each given object ofthe one or more objects comprises: extruding the two or more regions ofthe footprint based on a respective height value and based on the heightvalues corresponding to each respective region of the two or moreregions.
 4. The method of claim 1, wherein said extruding the respectivefootprint of each given object of the one or more objects comprisesshaping the top of the footprint based on zoning informationcorresponding to respective footprints.
 5. A system, comprising: aportable electronic device comprising: at least one processor; and amemory comprising program instructions, wherein the program instructionsare executable by the at least one processor to: receive two or moredata sets of mapping information for a map, wherein the two or more datasets of mapping information comprise two-dimensional mapping informationand three-dimensional mapping information, and wherein thethree-dimensional mapping information comprises three-dimensional meshdata comprising height information for one or more objects in the map;determine, based on the two or more data sets of mapping information,one or more spatial dimensions for the one or more objects in the map;generate, based on the one or more objects, a three-dimensional modelwith a level of granularity different from both the two-dimensionalmapping information and from the three-dimensional mapping information;and generate a map view based on the three-dimensional model; whereinthe map view is updated based on the created three-dimensional modelaugmented with computed model information for a new area displayed inthe map view as a result of the map view being updated.
 6. The system ofclaim 5, wherein to determine the one or more spatial dimensions theprogram instructions are further executable by the at least oneprocessor to: identify a footprint of an object from the two-dimensionalmapping information; correlate the footprint to a corresponding area inthe three-dimensional mapping information to find a height value; anddetermine, based on a height value, one of the one or more spatialdimensions.
 7. The system of claim 6, wherein to generate the map viewthe program instructions are further executable by the at least oneprocessor to: extrude the footprint to the height value; and for eachfootprint in the two-dimensional mapping information and a respectiveheight value, repeat the program instructions to extrude the footprintto the respective height value.
 8. The system of claim 5, wherein thelevel of granularity of the three-dimensional model is greater than alevel of granularity of one of the two or more sets of mappinginformation, and wherein the level of granularity of thethree-dimensional model is less than a level of granularity of anotherof the two or more sets of mapping information.
 9. A non-transitory,computer-readable storage medium storing program instructions, whereinthe program instructions are computer-executable to implement: receivingtwo-dimensional mapping information for a map, wherein thetwo-dimensional mapping information includes a footprint for an object;receiving three-dimensional mapping information for the map, wherein thethree-dimensional mapping information comprises three-dimensional meshdata for one or more locations in the map, and wherein thethree-dimensional mesh data includes height values corresponding to theone or more locations in the map; correlating a location of thefootprint of the object in the two-dimensional mapping information witha height value from the three-dimensional mapping information; extrudingthe footprint of the object to create a three-dimensional version of theobject based on the height value; and displaying a map view based on thethree-dimensional version of the object; wherein the map view is updatedbased on the created three-dimensional version of the object augmentedwith computed model information for a new area displayed in the map viewas a result of the map view being updated.
 10. The non-transitory,computer-readable storage medium of claim 9, wherein the programinstructions are computer-executable to further implement: repeatingsaid correlating for each footprint of each object in the map; repeatingsaid extruding for each footprint of each object in the map to createthree-dimensional versions of each object in the map; and displayingeach of the three-dimensional versions of each object in the map. 11.The non-transitory, computer-readable storage medium of claim 9, whereinthe program instructions are computer-executable to further implement:repeating said correlating for a plurality of locations of the footprintto determine a respective plurality of height values; and wherein saidextruding is based on an average value of the plurality of heightvalues; and wherein the height value is one of the plurality of heightvalues.
 12. The non-transitory, computer-readable storage medium ofclaim 9, wherein the program instructions are computer-executable tofurther implement: selecting the height value from among a plurality ofheight values corresponding to the footprint of the object.
 13. Thenon-transitory, computer-readable storage medium of claim 9, wherein thetwo-dimensional mapping information is vector data and not a rasterimage, and wherein the three-dimensional mapping information is vectordata and not a raster image.
 14. A method, comprising: performing, byone or more computing devices: creating a representation of an area of amap, wherein the representation is divided into a plurality of segmentsof a same size defined in terms of two-dimensional space; receivingthree-dimensional mapping information for the area of the map, whereinthe three-dimensional mapping information comprises three-dimensionalmesh data for one or more locations in the map, and wherein thethree-dimensional mesh data includes a plurality of height valuescorresponding to the one or more locations in the map; correlating asegment of the plurality of segments of the same size with a heightvalue of the plurality of height values from the three-dimensionalmapping information; adding a height dimension to the segment based onthe height value, wherein said creating, receiving, correlating, andadding are performed using a single source of mapping data comprisingthe three-dimensional mapping information; repeating said correlatingand said adding for each segment of the plurality of segments of thesame size; and displaying, based on the plurality of segments of thesame size, a three-dimensional view of the map; wherein thethree-dimensional view of the map is updated based on the createdthree-dimensional view of the map augmented with computed modelinformation for a new area displayed in the three-dimensional view ofthe map as a result of the three-dimensional view of the map beingupdated.
 15. The method of claim 14, wherein said correlating is basedon finding a location in the three-dimensional data set that correspondsto the segment of the plurality of segments of the same size.
 16. Themethod of claim 14, further comprising: determining a set of segments ofthe plurality of segments of the same size based on a correspondencebetween segments of the set of segments to a building footprint, whereinthe building footprint is specified within two-dimensional mappinginformation corresponding to the map.
 17. The method of claim 14,further comprising: generating, based on the plurality of segments ofthe same size, a three-dimensional model of the map; receiving inputcorresponding to a navigation operation within the displayedthree-dimensional view of the map; updating, based on the input and themodel, the three-dimensional view without receiving additional mappinginformation or without regenerating the model; and displaying theupdated three-dimensional view.
 18. The method of claim 14, wherein eachsegment of the plurality of segments of the same size corresponds to abuilding footprint.
 19. A method, comprising: performing, by one or morecomputing devices: receiving a plurality of data sets corresponding tomap related information; generating, based on the plurality of datasets, a three-dimensional model of a map, wherein the three-dimensionalmodel comprises one or more objects; displaying a map view based on thethree-dimensional model; receiving, through an interface, inputindicating a selection of an object in the three-dimensional model;invoking, based on the selection, a function that extracts data from oneor more of the plurality of data sets, wherein the one or more of theplurality of data sets comprises the three-dimensional model; andupdating the map view based on the function and based on the extracteddata; wherein the map view is updated based on the createdthree-dimensional model augmented with computed model information for anew area displayed in the map view as a result of the map view beingupdated.
 20. The method of claim 19, further comprising: displaying theupdated map view such that the object selected is highlighted, whereinhighlighting object comprises displaying the object contrasted againsteach of the other one or more objects in the updated map view.
 21. Themethod of claim 19, wherein said input corresponds to a change in avirtual camera perspective on which the map view is based.
 22. Themethod of claim 21, wherein said updating the map view comprisesgenerating, without receiving additional mapping information, a versionof the map view based on the virtual camera perspective.
 23. The methodof claim 19, further comprising: updating the map view in response touser input indicating a change in the map location, wherein saidupdating is based in part on the mapping information, and wherein saidupdating is based in part on new mapping information received inresponse to said indicating a change in the map location.